Copyright ã1992 by Scott Hess.  All Rights Reserved.

talk Isn't Working!

As part of starting up a subprocess, Stuart must store some information in system files and modify permissions on the tty device that the subprocess receives.  Many programs use this information to find out who the user is, and to allow communications between users.  If Stuart is not correctly installed, this information will be incorrect or non-existant, and the programs will not work.  The programs in question:

·	talk(1) will say `You don't exist.  Go away.' if there is not an /etc/utmp entry for the user.  This can happen if the slog tool is not correctly installed in the Stuart.app wrapper, or if the user turns off `Log to utmp' on the Subprocess pane of the inspector panels.

·	write(1) will say `write: username not logged in on that tty' if there is not an /etc/utmp entry for the user you are attempting to write to.  This can happen if slog is not properly installed, or if the user turns off `Log to utmp'.

·	biff(1) will say `/dev/tty**: Not owner.' if the subprocess' tty device has not had its permissions fixed.  This can happen if slog is not properly installed, or if the user turns off `Fix tty ownerships' on the Subprocess pane.

·	finger(1) not report a user if they have no utmp entry.  This is perhaps not a real problem, because there are valid reasons why users may not want to have a utmp entry for a particular subprocess.  If slog is not correctly installed, there is no possibility for such an entry to be generated.  who(1) also retrieves information from utmp.

·	who(1) can also make use of the /usr/adm/wtmp file.  If installed correctly, Stuart always records entries to the wtmp file.  If entries are not being recorded, suspect that slog is incorrectly installed.

·	last(1) also makes use of wtmp information.  If slog is not correctly installed, last will not correctly report last login times of users and tty devices.